Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds new integration [BassXT/xtool] #2999

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

Conversation

BassXT
Copy link

@BassXT BassXT commented Jan 11, 2025

Checklist

  • I've read the publishing documentation.
  • I've added the HACS action to my repository.
  • (For integrations only) I've added the hassfest action to my repository.
  • The actions are passing without any disabled checks in my repository.
  • I've added a link to the action run on my repository below in the links section.
  • I've created a new release of the repository after the validation actions were run successfully.

Links

Link to current release: https://github.com/BassXT/xtool/releases/tag/v1.0.0
Link to successful HACS action (without the ignore key): https://github.com/BassXT/xtool/actions/runs/12724540097
Link to successful hassfest action (if integration): https://github.com/BassXT/xtool/actions/runs/12724540095

Copy link

@hacs-bot hacs-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The submitted name bassXT/xtool does not match what GitHub returns for the repository (BassXT/xtool).

@hacs-bot hacs-bot bot marked this pull request as draft January 11, 2025 13:19
Corrected the repository name from "bassXT/xtool" to "BassXT/xtool" to ensure it matches GitHub's case sensitivity requirements.
@hacs-bot hacs-bot bot changed the title Update integration Adds new integration [BassXT/xtool] Jan 11, 2025
@hacs-bot
Copy link

hacs-bot bot commented Jan 11, 2025

Your repository is now waiting to be included in HACS. Please be patient, this will take some time.

You can see the current queue here (this is the order that is being used).

There is no need to:

  • Comment on the PR, the reviewer will get back to you.
  • Open a new PR, this will not speed up the process.
  • Ask your folowers to spam the PR, this will not speed up the process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant